Skip to content

[Snyk] Security upgrade @backstage/integration from 0.0.0-use.local to 0.1.0#5437

Closed
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-fc799809c474841cdbc8e935ddf076a2
Closed

[Snyk] Security upgrade @backstage/integration from 0.0.0-use.local to 0.1.0#5437
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-fc799809c474841cdbc8e935ddf076a2

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io Bot commented Jun 4, 2025

snyk-top-banner

Snyk has created this PR to fix 2 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • plugins/github-issues/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Origin Validation Error
SNYK-JS-WEBPACKDEVSERVER-10300775
  748  
medium severity Exposed Dangerous Method or Function
SNYK-JS-WEBPACKDEVSERVER-10300777
  693  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Summary by Sourcery

Bug Fixes:

  • Bump @backstage/integration dependency to version 0.1.0 in the GitHub Issues plugin to resolve high- and medium-severity webpack-dev-server vulnerabilities

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Jun 4, 2025

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@sourcery-ai
Copy link
Copy Markdown

sourcery-ai Bot commented Jun 4, 2025

Reviewer's Guide

This PR upgrades the @backstage/integration dependency in the GitHub Issues plugin from a workspace alias to a fixed version (0.1.0) to address Snyk-reported vulnerabilities and requires a manual yarn.lock update before merging.

Class Diagram: Update in dependencies of plugins/github-issues/package.json

classDiagram
    class `Dependencies in plugins/github-issues/package.json` {
        + "@backstage/integration": "String (updated to 0.1.0 from workspace:^)"
        + "@backstage/core-components": "String = workspace:^"
        + "@backstage/core-plugin-api": "String = workspace:^"
        + "@backstage/errors": "String = workspace:^"
        + "@backstage/plugin-catalog-react": "String = workspace:^"
        + "@backstage/theme": "String = workspace:^"
        + "...other dependencies": "String (unchanged)"
    }
Loading

File-Level Changes

Change Details Files
Bump @backstage/integration to 0.1.0 to resolve vulnerabilities
  • Changed dependency specifier from workspace:^ to 0.1.0
  • Removed the local workspace alias for @backstage/integration
  • Added note that yarn.lock must be updated manually
plugins/github-issues/package.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@socket-security
Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert (click for details)
Warn High
tree-sitter@=0.22.1 has a License Policy Violation.

License: Unicode-3.0 (package/vendor/tree-sitter/lib/src/unicode/LICENSE)

From: ?npm/tree-sitter@=0.22.1

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/tree-sitter@=0.22.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@snyk-io
Copy link
Copy Markdown
Author

snyk-io Bot commented Jun 4, 2025

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

"@backstage/core-plugin-api": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/integration": "workspace:^",
"@backstage/integration": "0.1.0",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change replaces the workspace reference with a fixed version, which breaks the monorepo dependency pattern. The other @backstage dependencies use workspace:^ to ensure consistent versioning within the project, while this change pins to a specific version 0.1.0 (which appears to be quite old for Backstage packages).

While addressing security vulnerabilities is important, changing the dependency resolution pattern may introduce other issues:

  1. It creates inconsistency in how dependencies are managed
  2. It may cause version conflicts during dependency resolution
  3. The fixed version might not be compatible with other workspace packages

Consider either:

  • Maintaining the workspace:^ pattern and updating the dependency in the workspace root
  • If a specific version is required for security reasons, verify that 0.1.0 is appropriate and document the exception

The warning about failing to update yarn.lock in the PR description suggests additional manual intervention will be needed before merging.

Suggested change
"@backstage/integration": "0.1.0",
"@backstage/integration": "workspace:^",

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

@github-actions
Copy link
Copy Markdown

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

@github-actions github-actions Bot added the stale label Jun 11, 2025
@github-actions github-actions Bot closed this Jun 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants